home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970626-19970929
/
000182_news@newsmaster….columbia.edu _Sun Aug 17 11:06:04 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA18975
for <kermit.misc@watsun.cc.columbia.edu>; Sun, 17 Aug 1997 11:06:03 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA20920
for kermit.misc@watsun; Sun, 17 Aug 1997 11:06:03 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: How do I start ckepage.ksc from command line
Date: 17 Aug 1997 15:05:59 GMT
Organization: Columbia University
Lines: 65
Message-ID: <5t740n$aas$1@apakabar.cc.columbia.edu>
References: <871757417.12783@dejanews.com> <5t4uc7$8a0$1@apakabar.cc.columbia.edu> <33F6EBE4.31AECA6E@ttsg.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7488
In article <33F6EBE4.31AECA6E@ttsg.com>, TTSG <ttsg@ttsg.com> wrote:
: Frank da Cruz wrote:
: > In article <871757417.12783@dejanews.com>, <ttsg@ttsg.com> wrote:
: > : I'm wondering now that I got the ckepage.ksc script working, how can I
: > : start it from a command line and include all the parameters for apage?
: > : I want to have a shell or perl script invoke it and just wait for the
: > : reply if it was good or bad.
: > :
: > See pages 353, 467-468, and 513 of "Using C-Kermit". Briefly, make the
: > script into an "application" or "shebang" file, and read the command line
: > arguments from the \&@[] array.
: >
: > - Frank
:
: Thanks for the quick and helpful reply! Having the pages to go directly
: to is great. One word though, the script at:
:
: ftp://kermit.columbia.edu/kermit/f/ckepage.ksc
:
: Is broken. It drove me nuts for almost 2 hours until I got enough
: debugging in it. What happened was I would get the ACK for the ESC-PG1,
: then it would stay in the loop and keep claiming timeouts. When I
: looked at it, I realized it couldn't work.... How did it ever get out of
: the for loop!?
:
: THERE IS A "BREAK" MISSING!
:
: for \%i 1 3 1 { ; Send <ESC>PG1, get <ACK>
: msl 500
: out \{27}PG1\13
: min 3 {\6\13} {\21\13} {\27\4\13}
: switch \v(minput) {
: :0, continue ; Timeout
: :1, break ; <ACK>
: :2, continue ; <NAK>
: :3, stop 1 Forced disconnect ; Fatal error
: }
: }
:
: SHOULD BE :
:
: for \%i 1 3 1 { ; Send <ESC>PG1, get <ACK>
: msl 500
: out \{27}PG1\13
: min 3 {\6\13} {\21\13} {\27\4\13}
: switch \v(minput) {
: :0, continue ; Timeout
: :1, break ; <ACK>
: :2, continue ; <NAK>
: :3, stop 1 Forced disconnect ; Fatal error
: }
: break
: }
:
You're right. I stuck this section of code into a loop a couple weeks
ago when I discovered a paging service that needed it (contrary to the
wording of the TAP specification) -- it lost characters galore and so
tended to miss the <ESC>PG1 reply, and so would need to see it again
(and again). Tests worked, of course :-)
Sorry for the confusion, updated script in the normal place:
ftp://kermit.columbia.edu/kermit/f/ckepage.ksc
- Frank